Problem Statement

Many hosts for Errata-UI, use a fixture registered_contenthost (@L223), which registers a rhel_contenthost fixture.
In parameterized sessions, the registered_contenthost can fail if preexisting content is present, so decent cleanup was needed.

• Current Errata-UI reg. hosts are setup as a fixture of a fixture,
• intermittent setup failures in the fixture, or mismatched/persisted content in CI runs.
• We do not seem to have a 6.15+ setup method like the older repos_collection.setup_virtual_machine() or ContentHost.contenthost_setup().

Solution

Create an API Factory method (could also exist in the ContentHost class?), that will accept desired entities to host content, associate them, then register the desired client (ie a passed fixture rhel_contenthost) to the now attached entities, using ak.

Note: For api-factory method, you can pass id (int), name (string), or instance for entities (except for client, must be the entity's instance, and except for boolean args)

Very minimal setup is needed, create the needed custom entities or import fixtures, add repos to CV prior if desired, then call the method. Prior to calling, you can also do varying amounts of custom setup to lce, CV etc. For CV, latest version (if any) will be used, can handle entities partially associated or fully.

• To enable repos for host, we can add them to the contentview like I did to setup test_end_to_end, then call the new function. Once registered, I enable them within the method by flag, and the repos (custom or redhat) will be visible to the host, from CV associated to AK. Can also skip enable_repos for method (default), and do it yourself after.
• Alternatively, using the method you can register to an empty CV, then add & sync repos in the CV, publish/promote, enable repos, content is now available to the registered client.
• You can also call other setup methods, like setup_org_for_a_custom_repo or setup_rh_repo_and_return_id etc,
  then simply add the repos to CV, before calling this new method. The content from repo(s) is associated and visible as expected.
• The method makes use of unittest MagicMock(), to mock a request to add finalizer (cleanup method to unregister host during teardown).
• You can register the host to entities using names: org, ak, env, cv
  ie: can accept str "Library" for environment, and can accept "Default Organization View" for content-view.
  Do not pass the Library env as an id or instance, this will fail (building a check for this). Done (ref ~@ln845)

Related Issues

• CI Intermittent UI failures of registered_contenthost, fails setup, or mismatched content, between parameters of a combined session.
• Difficulty creating/fixing tests, as many useful fixtures need varying levels of setup before they can be used to host content.

Demonstration-PRT Case

• UI::Errata::test_end_to_end : Implemented to replace existing registered_contenthost local fixture, which relies on convoluted setup to achieve a useable host ready for content/with content.

trigger: test-robottelo
pytest: tests/foreman/ui/test_errata.py::test_end_to_end